Thanks for tackling the label-catalog drift — but I think this PR has been overtaken by events and should likely be closed as superseded:

1. #711 is already resolved on main. Commit 791bdde refreshed docs/agent-context/labels.md and closed #711. The current canonical file documents the priority:, complexity:, area/, and type: families plus all topic labels, good-first-ai-issue, and area/gateway·area/cli·area/benchmarks·area/docs. This branch (cut before that landed) is now in merge conflict for that reason.
2. Merging would regress the canonical file. This version drops the type: family and ~25 topic labels, and switches priority:/complexity: to the slash form, whereas main treats the colon priority:<level> form as canonical and notes the slash/spaced variants as drift to consolidate.
3. The "30 live labels / 0 missing" check is truncated. gh label list defaults to 30 rows, but the repo has well over 30 labels — so the file omits many in-use labels and asserts type:feature/type:task/good-first-ai-issue are "not registered," when all three exist on the repo. The keep-current snippet has the same gap (add --limit 999).

If there's net-new content worth keeping (the milestone/ section, the gh label list keep-current snippet), please rebase onto main and layer just those additions on top of the current file — after fixing the --limit truncation and the "not registered" wording.

Generated by Claude Code

Approving — the rework fully addresses my earlier REQUEST_CHANGES. ✅

• Rebased onto main: the file now is main's canonical taxonomy (colon priority:/complexity:, the area/, type:, and topic-label families, plus both drift notes), with the PR layering only the net-new content on top. The diff is a clean +23 lines, and the earlier merge conflict is gone.
• Milestone section: verified the labels are real on the repo — milestone/v0.2, v1.0, and v0.5 all exist with matching descriptions.
• Keep-current snippet: now uses gh label list --limit 999, so the original 30-row truncation is fixed, and the "unregistered labels that may need canonicalisation" wording is accurate.

CI: all substantive checks are green (tests 3.10–3.13, Floor deps, Tool-run smoke ×2, Docs build, CodeQL, Analyze). The single red check — Post benchmark delta PR comment — is an infrastructure limitation, not a problem with this change: it fails with a 403 because a fork PR's GITHUB_TOKEN is read-only and can't post the comment. The job is explicitly non-blocking ("this comment never blocks the PR") and all benchmark deltas are neutral.

Optional, non-blocking nit: the Milestone table rows are ordered v0.2, v0.3, v1.0, v0.4, v0.5 — v1.0 is out of sequence. Worth a quick reorder if you touch the file again, but not worth holding the merge.

Generated by Claude Code